MarkLogic Server must generate audit records when successful logons or connections occur.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-220408	ML09-00-011100	SV-220408r961824_rule		Medium

Description
For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.

STIG	Date
MarkLogic Server v9 Security Technical Implementation Guide	2024-06-12

Details

Check Text ( C-22123r401675_chk )
Check the MarkLogic audit settings to verify whether an audit record is generated each time a user (or other principal) logs on or connects to the DBMS, this is a finding. Perform the check from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges. 1. Click the Groups icon. 2. Click the group in which the configuration to check resides (e.g., Default). 3. Click the Auditing icon on the left tree menu. 4. Inspect the audit enabled field. A value of false means auditing is not enabled and this is a finding. 5. If audit enabled field is true, but the authentication-failure event is not selected, this is a finding. 6. Under the Audit Restrictions - Outcome section, verify the security-access event for auditing is set to "both". If the setting is not "both", this is a finding. 7. If any roles, URIs, or users are identified in audit restrictions and not documented in the System Security Plan, this is a finding.

Check Text ( C-22123r401675_chk )

Check the MarkLogic audit settings to verify whether an audit record is generated each time a user (or other principal) logs on or connects to the DBMS, this is a finding.

Perform the check from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Groups icon.
2. Click the group in which the configuration to check resides (e.g., Default).
3. Click the Auditing icon on the left tree menu.
4. Inspect the audit enabled field. A value of false means auditing is not enabled and this is a finding.
5. If audit enabled field is true, but the authentication-failure event is not selected, this is a finding.
6. Under the Audit Restrictions - Outcome section, verify the security-access event for auditing is set to "both". If the setting is not "both", this is a finding.
7. If any roles, URIs, or users are identified in audit restrictions and not documented in the System Security Plan, this is a finding.

Fix Text (F-22112r401676_fix)
Configure MarkLogic audit settings to generate an audit record each time a user (or other principal) logs on or connects to the DBMS. Perform the fix from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges. 1. Click the Groups icon. 2. Click the group in which the configuration to check resides (e.g., Default). 3. Click the Auditing icon on the left tree menu. 4. Set the audit enabled field to true. 5. Enable the authentication-failure event for auditing. 6. Enable "both" for the audit restriction under the outcome selection. 7. Ensure no roles, URIs, or users are identified in the audit restrictions, unless documented in the System Security Plan.

Fix Text (F-22112r401676_fix)

Configure MarkLogic audit settings to generate an audit record each time a user (or other principal) logs on or connects to the DBMS.

Perform the fix from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Groups icon.
2. Click the group in which the configuration to check resides (e.g., Default).
3. Click the Auditing icon on the left tree menu.
4. Set the audit enabled field to true.
5. Enable the authentication-failure event for auditing.
6. Enable "both" for the audit restriction under the outcome selection.
7. Ensure no roles, URIs, or users are identified in the audit restrictions, unless documented in the System Security Plan.